An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi Apple, I hope you are doing well. I am posting here regarding our app, [Poker Reflex] (6761329446: [6761329446]), which has been stuck in the “Waiting for Review” state since [Friday 22th 2026]. We fully understand that App Review times can vary depending on workload and internal processes. However, in our case, the app has remained in this status for several days without any visible progress, update, rejection, metadata issue, or request for additional information. At the moment: No rejection message has been received No metadata issue is shown in App Store Connect No compliance or permission request appears to be pending No additional information has been requested from our side The app simply remains in “Waiting for Review” This is becoming a real concern for us because the delay is now significantly affecting our release planning and business timeline. We have carefully prepared the submission, reviewed the App Store Review Guidelines, and ensured that all required assets, metadata, permissions, and compliance information were provided. What concerns us most is that there seems to be no action or movement at all, which makes us wonder whether the submission may be stuck in the review queue or blocked by an unseen issue. We would sincerely appreciate any guidance from Apple or the developer community regarding: Whether this type of delay is currently common Whether there is any way to confirm that the app is properly queued for review Whether there may be an invisible issue preventing the review from starting Whether this can be escalated or checked by the App Review team We are fully available to provide any additional information or make immediate changes if something is required from our side. Any help, advice, or update would be greatly appreciated. Thank you. [Alexis / Poker Reflex Team]

Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.

This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { "errors": [{ "id": "80550434-590c-48c6-b2d3-5bd3b038539b", "status": "409", "code": "ENTITY_ERROR.RELATIONSHIP.INVALID", "title": "The provided entity includes a relationship with an invalid value", "detail": "The specified pre-release build could not be added.", "source": { "pointer": "/data/relationships/build" } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5​-2671​-44d6​-bacb​-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuck? The builds show as valid in TestFlight but cannot be attached to the App Store version.

Hi everyone! Today I finally submitted my first iOS app for App Store review after previously publishing the Android version on Google Play. App ID: 6771439707 The app was developed with Flutter and the process was a very interesting learning experience, especially around: App Privacy configuration screenshots and metadata archive/distribution process App Store Connect setup adapting branding/assets to platform guidelines Coming from Android publishing, I have to admit the Apple review pipeline feels much stricter and more detail-oriented 😄 but also very polished once everything is correctly configured. I just wanted to thank the community because many forum posts helped me solve issues during the submission process. Now waiting for review results 🤞 Greetings from Argentina!

Hi Apple, I hope you are doing well. I am posting here regarding my app, Subscription & Expense Manager (App ID: 6759901202), which has been stuck in the “Waiting for Review” state since March 4, 2026 at 2:45 PM. It has now been an extremely long time without any update, review progress, or communication from the App Review team, and I am becoming increasingly concerned about this unusual delay. I completely understand that review times may vary depending on workload and internal processes, but this duration seems far beyond normal review timelines. Our team has invested substantial time, effort, and resources into developing this application, and the continued delay is significantly affecting our launch plans and business timeline. We have carefully followed all App Store Review Guidelines and ensured that every required detail, asset, permission, and compliance item was properly submitted. At the moment: There are no rejection messages No metadata issues are shown No additional information requests are pending The app simply remains stuck in “Waiting for Review” We have also already contacted Apple regarding this matter but unfortunately have not yet received a response. I would sincerely appreciate it if someone from Apple or the developer community could guide me on: Whether this kind of delay is currently common If there is any way to escalate the issue Whether there may be an unseen issue causing the review to not start We are fully prepared to provide any additional information or make immediate changes if required from our side. This app is very important to us, and we are genuinely worried because of the extended delay after putting so much hard work into the project. Any help, advice, or update would be greatly appreciated. Thank you. HR Apps

My app has been in "Waiting for Review" status since May 8, 2026, and today is May 25, 2026. Before this, I had another submission that was uploaded on April 26, 2026, which also remained pending for a long time. I assumed there may have been an issue on my side, so I removed it and submitted a new build on May 8 — but the new build is still waiting as well.

Hello, My Paid Apps Agreement has been stuck in "In Process" status since May 16, 2026 — now 9 days with no resolution. I have received no emails from Apple regarding this The agreement has not been rejected The system does not allow me to make any edits I have contacted Apple Developer Support twice with no real response

Hi, Hi have released a new app on May 12th, that got reviewed and approved fairly fast (3 days after a single iteration for meta data content). On May 15th, I uploaded an update on the app, improving some feedback and user experience on one of the key features of it. I was expecting a similar delay (1-3 days) but it has been 10 already, and I have not had any contact from apple. My app is related with the World Cup, starting in 15 days, and this delay is working against it ... as I cannot market the app properly until it has the desired update. The submission id is 54d8dd83-8988-499e-964f-222ce9bb4cd3 Is there anyway of getting an answer from Apple on the reason why the review is taking so long?

Dear App Review Team, We are ShopBack mobile team. We submitted v6.12.0 on May 21 and it's been in "Waiting for Review" fo 4+ days. This is our second consecutive blocked release as v6.11.0 was rejected May 14 and never completed review, so our iOS users haven't received an update in 11 days. Here's what's sitting in this v6.12.0 build that's directly hurting users right now: Users who've had cashback claims rejected have no idea why. This release finally shows them the rejection reason. It's a financial app and our users deserve to know why their money wasn't credited. Users are hitting an intermittent crash during login due to a main-thread issue. This build fixes it. Users across 8 markets can't withdraw their cashback to airline miles. The feature is built and ready, just blocked. We've resolved all issues from the v6.11.0 rejection and are confident this submission is fully compliant. We're available to address any concerns immediately. Thank you for your time. Bundle ID: com.shopback.ShopBack | Apple ID: 1086505626 | Version: 6.12.0 (6120004) ShopBack Mobile Team

Hi Apple, I'm reaching out because my app Lynup (Bundle ID: ai.lynup.app, Apple ID: 6766385801) has been stuck in "Waiting for Review" since May 6, 2026 — that's now over 19 days with no movement. Here's what I've already tried: Submitted an expedited review request — twice Opened a support ticket with App Review (Case ID: 102892962160) on May 18, 2026 Despite both actions, the status hasn't changed and I haven't received any meaningful update beyond the initial acknowledgment. This is a first submission and the delay is significantly impacting our launch timeline. Any help, advice, or update would be greatly appreciated. Thanks in advance.

anyone else have this gltich? my app seems to be in stuck state and has not been reviewed for a week now. help?

I've got an app. I've gone to AppStore Connect and filled in everything I can think of (screenshots, encryption status, privacy nutrition label, description, categories, everything), and I can save. I want to actually get the thing submitted at least so beta testers can get it, and when I attach a build, the save button just goes to red bordered with an exclamation point in it. I don't see any error messages anywhere or underlined things. I've asked ChatGPT and Claude for guidance and tried all the things the mentioned, and I have had no luck. I've also tried three different builds -- one of them is about a month old at this point. I've tried contacting support for the last month with no luck. How can I figure out what's wrong so I can fix it?

Hello everyone, I'm facing a very frustrating situation with App Review for my indie app, CoffeePomodoro, and I'm hoping someone here or an Apple engineer can help shed some light on how to escalate and resolve this. My recent update (Version 1.3.1, Submission ID: 59763b52-7c14-4b27-a2cf-2799d2bafe35) was rejected under Guideline 3.1.1 - In-App Purchase. The rejection message states: "We found that the app includes a feature to restore previously purchased In-App Purchase products by entering the user's Apple Account and password. However, In-App Purchases cannot be restored in this manner." The Reality: There is absolutely zero custom UI, form, or TextField in my app that asks for an Apple ID or password. When a user taps "Restore Purchases", the app simply calls Purchases.shared.restorePurchases() via the RevenueCat SDK, which directly wraps Apple's native SKPaymentQueue.restoreCompletedTransactions(). The credential prompt the reviewer saw is the native iOS system-level authentication dialog that appears automatically in the sandbox/TestFlight environment. This usually happens if the device or simulator being used for the review doesn't have an active Sandbox Apple ID already logged in. I have explained this in the App Store Connect Resolution Center. I provided screen recordings showing it's the system dialog, and I attached code snippets proving the app only calls native APIs. Unfortunately, my explanations seem to be ignored, and I keep facing the same roadblock. It feels like the reviewers are mistaking their own OS's native prompt for a custom credential-harvesting screen. Meanwhile, my users are waiting for this update to resolve their subscription issues, and I am stuck in a rejection loop for using Apple's own native API exactly as intended. Has anyone else experienced this specific misunderstanding by the review team? How can I escalate this so someone actually reviews the screen recording and code snippets I provided? Thank you for your time.

Hi, My app ID: 6762301629 has been stuck in "Waiting for Review" since 17 May. We are worried there might be a system glitch or a hidden blocker holding up the process. Just wondering if there is anything we need to do on our end. Any help or a quick check from the App Review team would be greatly appreciated. Thank you!

Hi Team, My app ICY SIM (App ID: 6761278922) has been stuck in "Waiting for Review" for over 4 weeks with no movement, no feedback, and no communication. What I've done: Submitted multiple expedited review requests and resubmissions (I now understand this can reset queue position, so I've stopped doing that) Filed a support ticket 3 days ago (Case ID: 102895038326) — still no response I completely understand the team handles a high volume of requests. However, 4 weeks with zero communication — not even an acknowledgment of the support ticket — is concerning. What I'd like to know: Is there a system glitch, account flag, or hidden blocker preventing my submission from entering review? Can someone confirm my app is actually in the queue and not stuck due to a technical issue? A queue position or estimated timeline would go a long way Any visibility from the App Review team or anyone who has experienced a similar situation would be greatly appreciated. Thank you.

My app has been stuck in the “Waiting for Review” stage for the past 9 days, and I have not received any updates, feedback, or rejection notices. I have already contacted support multiple times regarding this issue, but unfortunately I have not received a response yet. I have spent a significant amount of time and resources building this app, including purchasing the required Apple Developer subscription and preparing everything according to the App Store guidelines. I kindly request you to please check my submission status or let me know if there is any issue causing the delay. Even a small update would be greatly appreciated. Case ID: 102893147964

Hi Team, My App : LuvLust: Couples Game & Quiz (App ID: 6747910861) has been stuck in "Waiting for Review" for 3-4 weeks with no movement, no feedback, and no communication. What I've tried: Multiple expedited review requests & resubmissions although I understand now that's not the best way as it resets my position. I understand there are lot of requests but a queue number or some form of communication would help. Just want to know if there is a system glitch, account flag, or hidden blocker preventing my submission from entering review. Any help from the App Review team would be greatly appreciated. Thank you.

Hey All, Having a terrible time trying to submit subscriptions to the App Store. Any help or guidance would be much appreciated. Setup Auto-renewable subscriptions (Monthly + Annual) and one non-consumable (Lifetime), all attached to first binary submission RevenueCat for IAP infrastructure What happened First submission (v2.26): all three IAPs attached cleanly to the binary submission via the "In-App Purchases and Subscriptions" section on the version page. Apple's review came back with feedback on the paywall display (Guideline 3.1.2c - auto-renewable subscription prices not visible). The reviewer's screenshot showed Lifetime rendering correctly with a price, but the two subscription rows blank. I was missing a localization setting, which I then fixed. The localization went into Waiting for Review, then back to Rejected again within hours - App Store Connect's UI explains this: items attached to a rejected app version submission cannot independently progress through review. I then cancelled the v2.26 submission, which freed the localization to be re-submitted standalone. That stuck. I built a new binary (v2.27) and uploaded to App Store Connect. When I opened the v2.27 version page, the "In-App Purchases and Subscriptions" section that Apple's documentation describes (and which appeared on v2.26) was no longer present. I couldn't find any UI way to attach the subscriptions to this version's submission. The subscriptions and localization remained in Waiting for Review from earlier, and the Draft Submission panel for v2.27 only listed the binary. I submitted the binary alone in the hope that Apple's backend would bundle the in-queue subs with this version's review (since they all reference v2.27). Apple's reviewer reported the same display behaviour I see in my own testing - Annual/Monthly blank, Lifetime shown - and rejected on Guideline 2.1(b). What I've tried Resaving + resubmitting the group and per-subscription localizations Replying via Resolution Center with detailed context Updated App Review notes explaining the dependency between the subs and the binary Re-recorded the paywall screen recording on the current build Confirmed Paid Apps Agreement is Active and Tax / Banking are complete Completed a previously-incomplete "Sharing Economy Reporting Regime" compliance row that was in Missing Info (doesn't apply to my app, but flagged complete to rule it out) Sandbox testing on the iOS simulator with a sandbox tester signed in via Developer → Sandbox Apple Account: Lifetime renders its price, Monthly/Annual remain blank (same as Apple's review environment) Verified all product configuration in App Store Connect - pricing across territories, intro offers, localized display names + descriptions, review screenshots are all present Verified the RevenueCat offering correctly references the product IDs and the "pro" entitlement is properly linked Questions Is there a way to surface the "In-App Purchases and Subscriptions" attachment section on a new version after the first version was rejected? Something I'm missing in the configuration? For subscriptions sitting in Waiting for Review that are tied to a now rejected version, is there a way to attach them to a new version submission so they're reviewed together? If recreate with new IDs is the only path, is there any way to preserve the original product IDs for the subscription identifiers eventually, or are they permanently consumed? Thanks all, Cheers r

Hey everyone, Starting to get a bit anxious here. Our app has been stuck in “In Review” for an unusually long time, and we haven’t received any updates or communication from Apple yet. Usually reviews are much faster for us, so this delay has us worried that something may be wrong or stuck in the process. We have an important release planned, and the uncertainty is honestly stressful. Has anyone else experienced unusually long review times recently? Did your app eventually go through, or did you have to contact Apple? Would really appreciate hearing others’ experiences. Thanks 🙏

As a game studio with real business commitments, we depend on a predictable App Review process. Every month, we publish updates, run user acquisition campaigns, and test new ideas; that’s how our business operates. It’s not optional. We have obligations to our partners, our marketing budgets are committed in advance, and our entire monthly rhythm depends on getting builds out on schedule. Right now, Apple’s App Review is making that impossible. For the past 30 days, we’ve been stuck in a rejection loop on a single submission. Here’s what the cycle looks like: • Apple rejects our build with vague, generic feedback that doesn’t actually identify what’s wrong. • We investigate every possible scenario that could conceivably match their description, fix what we believe is the issue, and resubmit, usually within three hours. • Then we wait. And wait. Each review of the resubmission takes more than ten days. Read that again: we respond in 3 hours, they respond in 2 weeks. This isn’t a one-off. It’s been three full cycles now, and we still don’t have clarity on what they actually want changed. The rejection notes are so shallow that we’re forced to guess; patch a plausible cause, ship it, and hope. It honestly feels like reviews are being triaged by AI models that aren’t ready for the job yet: surface-level pattern matching, no real engagement with the build, no specifics we can act on. Meanwhile, the cost is real: • UA campaigns we’ve already committed budget to are bleeding out. • Partner deliverables are slipping. • Our team’s monthly release rhythm — the engine of how we operate as a business — is broken. • We’re paying engineers to play guessing games with a reviewer who won’t tell us what’s wrong. We’ve escalated everywhere we can. Contact forms, appeals, developer support, every channel Apple offers. Nothing has moved. We love the platform. We want to keep shipping great games on iOS. But Apple needs to understand that App Review isn’t just a gatekeeping checkbox, it’s a load-bearing piece of every developer’s business operation. When a single rejection cycle eats 10+ days and the feedback isn’t actionable, you’re not protecting users. You’re breaking the businesses building for your platform. Two things need to change, urgently: 1. Restore meaningful, specific rejection feedback. Tell us exactly what’s wrong, with reproduction steps. If a human reviewer can’t be specific, an AI definitely shouldn’t be making the call. 2. Prioritize resubmissions on an in-flight review. A 10-day turnaround on a fix to a rejection you issued, three hours earlier, is indefensible. These should jump the queue, not start at the back. If anyone at Apple is reading this: we’re trying to work with you. Please help us help you. Want me to tighten it, make it angrier, soften it, or pull out the bullet lists so it reads as straight prose for the forum?